The server instances table allows admins to view and manage the services that are part of the cluster deployment. Since the routing application will send requests across the cluster using this table, it is critical that it remains current.
Warning: Multi-server deployments are only available with the Enterprise edition. If a multi-server deployment is detected with the Community or Standard editions, the application will stop functioning. In this scenario, use the instances table to remove the irrelevant multi-server nodes.
This page is accessed from the Admin Console:
- Go to Services > Server Instances.
- Filter the list as required, using the drop-down lists at the top-left of the page.
Macro Buttons (top-right)
The macro buttons along the top-right are used to apply a function to multiple services:
- Run Garbage Collector: Free up memory by removing unused items. When run from the macro buttons, the garbage collector cleans up items from all services. It can also be run for a specified service from the Diagnostic Dashboard.
- Show Unreachable Services: Shows services that cannot be reached.
- Delete: Delete the selected services. For more information, see Deleting Server Nodes.
Server Instance Filters
Use the drop-down lists to include only server instances on a particular machine or associated with a particular service in the view.
Server Instance Details
|
Name |
Description |
|---|---|
|
Status |
Shows whether the service is accessible from the central router. |
|
Caption |
The friendly name given to the service. Click Edit to change the name of the service node. |
|
Active Memory (MB) |
The amount of memory the service is currently consuming in megabytes (MB) |
|
Memory Limit (MB) |
The maximum amount of memory the service is allowed to consume. Click Edit to change the upper memory limit. For more information, see Service Memory Limits. |
|
Type |
The type of service. |
|
Name |
The technical name for the service. |
|
Address |
The network address for the machine. Either an FQDN or IP Address. Click Edit to change the address of the server hosting the service. Warning: Changing this to the wrong address could break the cluster. |
|
Create Date |
The date the service was added to the cluster. |
|
Machine Local Time |
The current time as configured on the hosting machine of the service. Use this to diagnose scheduling issues. |
Managing Server Nodes
You can edit the following server nodes in this page
- Edit the Caption to change the name of the service node.
- Edit the Address to change the address of the server hosting the service. This can be either an IP address or FQDN. Note: changing this to the wrong address could break the cluster.
- Edit Memory Limit to open a dialog allowing admins to change the upper memory limit (measured in Megabytes). For more information, see Service Memory Limits.
Deleting Server Nodes
Warning: To keep the application viable, at least one node for a given service needs to remain operational.
There are two mechanisms for deleting server nodes in the server instance page:
- Click Delete alongside any row to delete a single server node.
- Select the servers that you want to delete using the checkboxes to the left, and click Delete at the top-right of the page.
In either case, the system will NOT allow you to delete any type of node if there is only one node in the cluster.
Tip: If you want to remove a node and you are prevented (as described above), install a second node into the cluster and then return to this panel to remove the previous node.
Restarting Server Nodes
The action buttons to the left of each server instance in the table can be used to Restart the individual server nodes. For more information about restarting server nodes, including information about when you might want to restart server instances, see Restarting Platform, Service Types, and Service Instances.
Audit Logging
If audit logging is enabled, click Audit Log to see the audit trail history for the service object. For more information, see Audit Trail Framework.